jmacorp.com > system selection > requirements definition

Phase 1 - Requirements Definition

  1. Planning Session

    This meeting is used to develop a clear understanding between you, the client, and J. Martin & Associates, Inc. The scope of the project is completely defined and the approach is outlined. A project time line will be developed and agreed upon and a budget will be determined for the total project. We’ll define and discuss the objectives of the project to form a solid basis for a successful project.
     
  2. Project Kickoff

    In this session we’ll determine the number and length of each internal user interview and the topics that will be discussed. A schedule is developed so that users know when and for how long they will be interviewed. Occasionally, questionnaires are distributed at this meeting so the users may do some preliminary work on the project before the interview
     
  3. Interviews

    Each key user is interviewed and functional requirements for the user’s position are documented. It is very important that the user step out of the current processing environment and begin to visualize how things could be done differently and more effectively. We’ve learned that it’s best to have a third party conduct these interviews because users often get tunnel-vision very quickly and aren’t able to see alternative methods of performing a job or task.
     
  4. Compilation

    The functional requirements from each interview are compiled and reviewed for completeness. Ordinarily, there are a few follow up interviews to fill in missing information or round out the functionality of a given area since almost all positions share information in an integrated system. The functional requirements are sorted into logical modules relating to software modules.