Process Modeling




 Process Modeling

Process modeling involves graphically representing the processes, or actions, that capture, manipulate, store, and distribute data between a system and its environment and among components within a system. A common form of a process model is a data-flow diagram (DFD). A data-flow diagram is a graphic that illustrates the movement of data between external entities and the processes and data stores within a system. Although several different tools have been developed for process modeling, we focus solely on data-flow diagrams because they are useful tools for process modeling. Data-flow diagramming is one of several structured analysis techniques used to increase software development productivity. Although not all organizations use each structured analysis technique, collectively, these techniques, like dataflow diagrams, have had a significant impact on the quality of the systems development process.

Modeling a System’s Process

The analysis team begins the process of structuring requirements with an abundance of information gathered during requirements determination. As part of structuring, you and the other team members must organize the information into a meaningful representation of the information system that exists and of the requirements desired in a replacement system. In addition to modeling the processing elements of an information system and transformation of data in the system, you must also model the structure of data within the system (which we review in Chapter 7). Analysts use both process and data models to establish the specification of an information system. With a supporting tool, such as a CASE tool, process and data models can also provide the basis for the automatic generation of an information system.

Topics You May Be Interested In
System Development Life Cycle (sdlc) Introduction
Types Of Documentation And Their Importance Architectural Patterns
Mobile And Ubiquitous Computing Executing The Project-managing The Information Systems Project
Distributed Multimedia Systems Using Project Management Software
Focus On Resource Sharing Building The Baseline Project Plan

Deliverables and Outcomes

In structured analysis, the primary deliverables from process modeling are a set of coherent, interrelated data-flow diagrams. Table 6-1 lists the progression of deliverables that result from studying and documenting a system’s process. First, a context data-flow diagram shows the scope of the system, indicating which elements are inside and outside the system. Second, data-flow diagrams of the current system specify which people and technologies are used in which processes to move and transform data, accepting inputs and producing outputs. The detail of these diagrams allows analysts to understand the current system and eventually to determine how to convert the current system into its replacement. Third, technology-independent, or logical, data-flow diagrams show the dataflow, structure, and functional requirements of the new system. Finally, entries for all of the objects in all diagrams are included in the project dictionary or CASE repository.

TABLE 6-1: Deliverables for Process Modeling

Process Modeling

Topics You May Be Interested In
Real Time And Distributed System Closing Down The Project-managing The Information Systems Project
Cost-benefit And Analysis -tools And Techniques Calculating Expected Time Durations Using Pert-representing And Scheduling Project Plans
Financial Trading Assessing Project Feasibility
Mobile And Ubiquitous Computing Building The Baseline Project Plan
Architectural Models Performing Requirements Determination

This logical progression of deliverables helps you to understand the existing system. You can then reduce this system into its essential elements to show the way in which the new system should meet its information processing requirements, as they were identified during requirements determination. In later steps in the systems development life cycle, you and other project team members make decisions on exactly how the new system will deliver these new requirements in specific manual and automated functions. Because requirements determination and structuring are often parallel steps, data-flow diagrams evolve from the more general to the more detailed as current and replacement systems are better understood. Even though data-flow diagrams remain popular tools for process modeling and can significantly increase software development productivity, they are not used in all systems development methodologies. Some organizations, such as EDS, have developed their own type of diagrams to model processes. Some methodologies, such as rapid application development (RAD), do not model processes separately at all. Instead, RAD builds processes—the work or actions that transform data so that they can be stored or distributed—into the prototypes created as the core of its development life cycle. However, even if you never formally use data-flow diagrams in your professional career, they remain a part of systems development’s history. DFDs illustrate important concepts about the movement of data between manual and automated steps and are a way to depict work flow in an organization. DFDs continue to benefit information systems professionals as tools for both analysis and communication. For that reason, we devote this entire chapter to DFDs.

 

 

 

Topics You May Be Interested In
Systems Models Types Of Models - Systems Environment And Boundaries Planning The Project-managing The Information Systems Project
Scope And Classification Of Metrics Representing And Scheduling Project Plans
Architectural Elements Building The Baseline Project Plan
Examples Of Distributed Systems Pine Valley Furniture Webstore: Systems Planning And Selection
Initiating The Project-managing The Information Systems Project Modern Methods For Determining System Requirements

 

 

 

 

Topics You May Be Interested In
System Definition And Concepts | Characteristics And Types Of System Openness
Systems Models Types Of Models - Systems Environment And Boundaries Quality Of Service
Role And Need Of Systems Analyst Architectural Patterns
Scope And Classification Of Metrics Calculating Expected Time Durations Using Pert-representing And Scheduling Project Plans
Characterization Of Distributed Systems Pine Valley Furniture Webstore: Determining System Requirements

 

 

 

 

Topics You May Be Interested In
Various Phases Of Development - Analysis, Design, Development, Implementation, Maintenance Openness
Types Of Feasibility Studies And Feasibility Reports Summary
Software Measuring Process And Product Attributes Architectural Elements
What Is Information Systems Analysis And Design? Examples Of Distributed Systems
Examples Of Distributed Systems Radical Methods For Determining System Requirements

 

 

 

 

Topics You May Be Interested In
System Definition And Concepts | Characteristics And Types Of System Reuse-systems Acquisition
Types Of Documentation And Their Importance Pine Valley Furniture Company Background-managing The Information Systems Project
Types Of Feasibility Studies And Feasibility Reports Initiating And Planning Systems Development Projects
Web Search Assessing Project Feasibility
Massively Multiplayer Online Games (mmogs) Pine Valley Furniture Webstore: Determining System Requirements

 

 

 

 

Topics You May Be Interested In
System Development Life Cycle (sdlc) Physical Models
System Selection Plan And Proposal Prototyping Architectural Elements
Scope And Classification Of Metrics Architectural Patterns
Openness The Process Of Identifying And Selecting Information Systems Development Projects-identifying And Selecting Projects
Failure Handling Pine Valley Furniture Webstore: Systems Planning And Selection

 



Frequently Asked Questions

+
Ans: Whether traditional or modern, the methods for determining system requirements that you have read about in this chapter apply to any requirements determination effort, regardless of its motivation. view more..
+
Ans: Even though we called interviews, questionnaires, observation, and document analysis traditional methods for determining a system’s requirements, all of these methods are still used by analysts to collect important information. view more..
+
Ans: Collection of information is at the core of systems analysis. view more..
+
Ans: Process modeling involves graphically representing the processes, or actions, that capture, manipulate, store, and distribute data between a system and its environment and among components within a system. view more..
+
Ans: Data-flow diagrams are versatile diagramming tools. view more..
+
Ans: Sofware engineering syllabus The course of the program is designed in an exceedingly manner that it covers all the aspects of software system engineering needed for higher understanding of the scholars. The delivery methodology of the program is usually schoolroom lectures Associate in Nursing sensible laboratory sessions beside seminars and internships being an integral a part of the course. BE/B.Tech software system Engineering give students data of evaluating the correct codes and software system for specific tasks. view more..
+
Ans: The first published model of software development process was derived from more general system engineering processes. Because of the cascade from one phase to another, this model is known as the waterfall model or software life cycle. The principal stages of the model map onto fundamental development activities: view more..
+
Ans: System prototyping performs the analysis, design, and implementation phases concurrently in order to quickly develop a simplified version of the proposed system and give it to the users for evaluation and feedback. view more..
+
Ans: Software is defined as collection of data, programs, procedures, associated documentaion and rules. which does not have any mass, volume and colour. software does not wear out,get tired or degrade over a long period of time view more..



Recommended Posts:


Rating - NAN/5
489 views

Advertisements