Scribd
Upload
15 views

I. Initial Phase or Requirements Phase: (A) Tasks: (B) Roles

The document describes the initial requirements phase of a project. It involves gathering requirements from customers with the help of a business analyst and templates. The engagement manager ensures all requirements are clear and handles any extra costs. The output is a requirements document by various names. The analysis phase then involves feasibility studies, planning, technology selection and detailed requirements analysis. The output is a system requirements specification document.

Uploaded by

Jagat Mishra
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
15 views

I. Initial Phase or Requirements Phase: (A) Tasks: (B) Roles

The document describes the initial requirements phase of a project. It involves gathering requirements from customers with the help of a business analyst and templates. The engagement manager ensures all requirements are clear and handles any extra costs. The output is a requirements document by various names. The analysis phase then involves feasibility studies, planning, technology selection and detailed requirements analysis. The output is a system requirements specification document.

Uploaded by

Jagat Mishra
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

I.

Initial Phase or Requirements Phase :

(a) Tasks: Interaction with the customer and gathering the requirements.

(b) Roles: Business Analyst (B.A), Engagement Manager (E.M)


Process: First of all the business analyst will take an appointment from the customer,
collects the templates from the company, meets the customer on appointed day, gathers
the requirements with the help of template and comes back to the company with the
requirements documents.

Once the requirement document has come to the company the


engagement manager will check whether the customer gives any extra requirements or
confused requirements. In case of extra requirements he deals the excess cost of the
project. In case of confused requirements he is the responsible for prototype
demonstration and gathering the clear requirements.

Proof: The proof document of this phase is Requirements Document. This is called
with different names in different companies.

1. FRS (Functional Requirements Specification)

2. CRS (Customer Requirement Specification)

3. URS (User Requirement Specification)

4. BDD (Business Design Document)

5. BD (Business Document)

6. BRS (Business Requirement Specification)

Some companies may maintain the over all business flow information in one document
and the detailed functional requirement information in the other document

Templates: It is a pre defined format, which contains the predefined fields, and
used for preparing a document in an easy, comfort and perfect manner.

Prototype: -Defined as a roughly & Rapidly developed model which is used for
demonstrating to the client, In order to gather the clear requirements and to win the
confidence of a customer.

II. Analysis Phase:

(a) Tasks:
1. Feasibilty Study

2. Tentative planning
1. Technology Selection

2. Requirement Analysis
(b) Roles: System Analyst, Project Manager, and Team Manager.

Process

1. Feasibility Study: - It is detailed study of the requirements in order to check


weather the requirements are possible or not.

2. Tentative Planning: In this section the resource planning and the time
planning (scheduling) is done temporarily.

3. Technology Selection: - The list of all the technologies that are required to
accomplish this project. Successfully will be analyzed and listed out in this
section.

4. Requirement Analysis: - The list of all the requirements that are required to
accomplish this project. Successfully will be analyzed and listed out here in this
section.

SRC- System requirement specification

Proof: - The proof of this phase is system Requirement specification.

You might also like