Home ] in house classes ] in house courses ]

END-USER REQUIREMENTS DEFINITION 

The information systems developer faces many of the same issues as the conventional architect. He or she must work with information systems clients to define a system that will truly serve their needs. Those needs, however, may be only vaguely defined or not well understood. The clients rarely know what their systems should look like at the beginning of the development effort. Rather, the developer and the client must work together to define the application. Communication is a real problem. Clients use application terms that are unfamiliar to the developer; developers use data processing terms that are unfamiliar to the client. The quality of the terminology is not the only issue: the developer must also manage a barrage of details pertaining to the proposed system. Keeping track of all the details and deciding which are the most important can easily overwhelm a development project.

To solve these problems, we created the Warnier/Orr Data Structured Systems Development Methodology. Based on a handful of easily understood principles, this method has been used by hundreds of organizations worldwide to build better systems.

The portion of the Warnier/Orr methodology examined in this seminar —the End-User Requirements Definition phase— relates to the capture and organization of client requirements. It provides a complete set of simple, but powerful, analysis techniques that improve communication between client and developer. This methodology helps end users and developers capture complete, correct, and unambiguous requirements for even the most complex systems.

The Warnier/Orr Requirements Definition phase uses a variety of easy-to-use graphic communication tools. The nontechnical methods employed in the phase help establish the results that the proposed system must produce. The process enables clients and system developers to speak a common language, and to reach agreement on the shape of a system before building it. Its emphasis on results and its data-oriented approach create systems that are effective, complete, and satisfy the client's needs. Since the Requirements Definition process is predictable, project planning and project management become more effective.

The End-User Requirements Definition seminar is an intensive three-day workshop. It is presented with many examples, exercises, and case studies that give the student a practical working knowledge of the requirements definition process. Its largely nontechnical approach makes it a suitable workshop for both systems developers and their end-user clients.

COURSE  INFORMATION   

Who Should Attend 

 Information systems clients and users, user management, requirements analysts, systems developers, systems analysts, programmer/analysts, project leaders, and project managers.

 

  Course Length

Three days divided into 6 segments of 3 hours each, with lunch and coffee breaks.

Course Outline

1. Introduction
2. Background
A. Communication                
3. Fundamental Concepts
A. Development Principles
    1. Output Oriented
    2. Logical vs. Physical
    3. Data Oriented     
B. Terminology                   
    1. Sets and Subsets
    2. Mappings            
C. Objectives                        
4. Tools  
 A. Actor/Message Diagrams
   1. Actors and Messages
B. Warnier/Orr Diagrams
5. Methodology
A. Statistics                                
   1. Client-Level A/M Diagrams
   2. Combined A/M Diagrams
   3. Application-Level A/M Diagrams
B. Dynamics                          
    1. Positive Functional Flows
    2. Defining Scope  
    3. Detailed Functional Flows
C. Feedback & Control       
     1. Exception Functional Flows
D. Outputs                               
     1. Local Output Definition
       a. Prototyping
       b. Data Analysis
       c. Logical Output Structures
     2. Global Output Definition
        a. Synonyms and Homonyms
        b. Logical Output Base
E. Design Overview            
     1. Logical Data Design
      2. Logical Process Design
6. Case Study Exercise
7. Conclusion
A. Getting Started                 
 B. Critical Success Factors

 

Other courses available on the  

Warnier/Orr Data Structured Development Methodology 

Data Structured Program Design

Data Structured Systems / Data Base Design

Data Structured Software Maintenance

 These classes are available for presentation in an in-house format; they may be offered as  public courses if there is sufficient interest in a particular geographic area. For availability and pricing, please call us at   785 . 228 .1200.

 

Home ] in house classes ] in house courses ]

  The Ken Orr Institute  

5883 S.W. 29th St., Suite 101, Topeka, KS 66614

Phone: 785.228.1200 Fax: 785.228.1201
Email: webmaster@kenorrinst.com

kenorr@kenorrinst.com