CORE BUSINESS

Requirements Analysis

Knowledge Link approaches requirements analysis with the basic question:  What is the software, product, or project supposed to do (or accomplish)?  The Knowledge Link Requirements Analyst then proceeds to:

• Enumerate functional specifications

• Reconcile differences among individuals and stakeholders

• Translate the wants of prospective users into technical specifications for the project team

• Prepare cost estimates

• Reconcile wants with resources available   

In enumerating all the functional specs, the Knowledge Link Requirements Analysis asks clients and stakeholders to articulate use cases or scenarios.  A use case is a narrative that describes how the software, product, or project should behave or perform in different circumstances from different perspectives.  All the different stakeholders should be represented.  Unlikely as well as likely scenarios should be considered.  The requirements analyst then culls functional specifications from the use cases. 

The following are examples of functional specs: 

• The system should be accessible by the client's customers over the Internet. 
• The client's accounting/finance department needs real-time access to the system's financial data.
• Once a shipment has been properly authorized, a pick list/packing slip should be printed on the warehouse floor.
• Unauthorized access to certain data needs to be prevented at all costs.

Examples of technical specs are as follows:

• The system needs a secure Web site for customers to log in and file orders and reports.
• Order forms served on the Web site will contain the following fields, field lengths and data types. 
• Order item numbers, descriptions, and quantities available on the order form will be updated in real time from the client's Oracle inventory database.