Web IS Development Methodology (WISDM):WISDM and the IS development life-cycle

By -
3.5 WISDM and the IS development life-cycle

WISDM covers the analysis and design activities of system development. An IS development project also encompasses the construction of software and its operation and maintenance (figure 3.3). Software construction is discussed in chapter 10. There must also be testing and implementation, followed by operations and monitoring. These are largely outside the scope of this book, but they are essential aspects of the IS development life-cycle. There is no unidirectional flow seen in figure 3.3. The different life-cycles discussed in chapter 2 – waterfall, iterative, and evolutionary – are catered for in WISDM dynamics since all approaches must address the basic issues of analysis and design, software construction and implementation, and operation and maintenance. Thus, the traditional waterfall life-cycle is a special case: a requirements specification is produced and frozen and then passed on for refinement into a design and implementation in subsequent stages of the life-cycle. The specification might also be produced iteratively through RAD or evolve through successive prototypes.

Running throughout any IS development project is a concern for project management and quality management. This might be formalized as, for example, in PRINCE, the UK Government sponsored project management methodology, and the ISO9000 series of quality standards, or it might be less formal, for example, being driven by customer expectations and self-organizing teams.

Comments

Post a Comment

Popular posts from this blog

The Conversion Cycle:The Traditional Manufacturing Environment

By -
Image
The Traditional Manufacturing Environment The conversion cycle consists of both physical and information activities related to manufacturing products for sale. The context-level data flow diagram (DFD) in Figure 7-1 illustrates the central role of the conversion cycle and its interactions with other business cycles. Production is triggered by customer orders from the revenue cycle and/or by sales forecasts from marketing. These inputs are used to set a production target and prepare a production plan, which drives production activities. Purchase requisitions for the raw materials needed to meet production objectives are sent to the purchases procedures (expenditure cycle), which prepares purchase orders for vendors. Labor used in production is transmitted to the payroll system (expenditure cycle) for payroll processing. Manufacturing costs associated with intermediate work-in-process and finished goods (FG) are sent to the general ledger (GL) and financial reporting system. Dependin...
Read more

The Revenue Cycle:Manual Systems

By -
Image
Manual Systems The purpose of this section is to support the system concepts presented in the previous section with models depicting people, organizational units, and physical documents and files. This section should help you envision the segregation of duties and independent verifications, which are essential to effective internal control regardless of the technology in place. In addition, we highlight inefficiencies intrinsic to manual systems, which gave rise to modern systems using improved technologies. SALES ORDER PROCESSING The system flowchart in Figure 4-12 shows the procedures and the documents typical to a manual sales order system. In manual systems, maintaining physical files of source documents is critical to the audit trail. As we walk through the flowchart, notice that in each department, after completion of the assigned task, one or more documents are filed as evidence that the task was completed. Sales Department The sales process begins with a customer cont...
Read more

Nassi-Shneiderman charts

By -
Image
Nassi-Shneiderman charts 56.1 Purpose Nassi-Shneiderman charts were developed by Nassi and Shneiderman as an alternative to traditional logic flowcharts. Their intent was to provide a structured, hierarchical, graphical view of the flow of logic through a program, a routine, a module, or a process. Nassi-Shneiderman charts are used to document, plan, and design detailed program logic. 56.2 Strengths, weaknesses, and limitations A properly prepared Nassi-Shneiderman chart can illustrate the flow of logic through a module or routine at a glance. Nassi-Shneiderman charts are useful for describing or planning relatively small modules, routines, or processes. They can be used to clearly show nesting and recursion, and are easily converted to structured code. Nassi-Shneiderman charts should not be used for documenting complete programs or large routines. As a general rule, Nassi-Shneiderman charts should be limited to a single page with no more than 20 subdivisions. For larger rout...
Read more