Business Requirements Statement

1. Business Requirements Statement Interpersonal Skills and Communications

2. Business Requirements Statement • A consolidation of all system models, discovery prototypes, and supporting documentation is sometimes called a requirements statement. • All elements of the requirements statement are stored in the repository, but most systems analysts find it useful to keep a printed copy of that documentation for reference and reporting.

3. Interpersonal Skills and Communications • Written Reports • The business and technical report is the primary method used by analysts to communicate information about a systems development project. • The purpose of the report is to either inform or persuade, possibly both.

4. Systems Analysis Reports • The definition phase results in a business requirements statement. • This specification document is often large and complex and is rarely written up as a single report to system users and owners. • It is best reviewed in walkthroughs (in small pieces) with users and maintained as a reference for analysts and programmers.

5. Organizing the Written Report • Every report consists of both primary and secondary elements. • Primary elements present the actual information that the report is intended to convey. Examples include the introduction and the conclusion. • Secondary elements package the report so the reader can easily identify the report and its primary elements. Secondary elements also add a professional polish to the report.

7. The abstract or executive summary is a one- or two-page summary of the entire report. • The introduction should include four components: purpose of the report, statement of the problem, scope of the project, and a narrative explanation of the contents of the report. • The methods and procedures section should briefly explain how the information contained in the report was developed — for example, how the study was performed or how the new system will be designed. • The bulk of the report will be in the facts section. • This section should be named to describe the type of factual data to be presented (e.g., “Existing Systems Description,” “Analysis of Alternative Solutions,” or “Design Specifications”). • The conclusion should briefly summarize the report, verifying the problem statement, findings, and recommendations.

8. Sample Outline for a Requirements Statement • Executive Summary • Introduction (milestone 1) • Background (milestone 2) • Business requirements (milestone 3) • Feasibility Study (milestone 4) • Proposed design phase plan and schedule • Appendix

9. Formal Presentations • In order to communicate information to the many different people involved in a systems development project, a systems analyst is frequently required to make a formal presentation. • Formal presentations are special meetings used to sell new ideas and gain approval for new systems. They may also be used for any of the purposes in the margin. In many cases, a formal presentation may set up or supplement a more detailed written report.

10. Preparing for the Formal Presentation • Step 1: Define your expectations of the presentation — for instance, that you are seeking approval to continue the project, that you are trying to confirm facts, and so forth. • A presentation is a summary of your ideas and proposals that is directed toward your expectations. • Step 2: Organize your presentation around the allotted time (usually 30 to 60 minutes).

11. Preparing for the Formal Presentation (cont.) • Step 3: Prepare visual aids such as predrawn flip charts, overhead slides, Microsoft Powerpoint slides and the like — to support your position. • Step 4: Practice the presentation in front of the most critical audience you can assemble.