Whitepaper - Project Analysis Process at Konstant

395 views

Published on

This document will guide you about the procedures that Konstant follow in the Requirement Gathering Phase once the project is awarded to Konstant. As Konstant understands that requirement gathering is a vital part of successful project management and application development. We don’t want to blame the customers for not being sufficiently clear about their business requirements. Sometime clients/users are guided through a process that elicits their business requirements and facilitates accurate application development, but our analysts are well versed in both understanding the concepts of business requirement gathering AND the process that will best document them.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

Whitepaper - Project Analysis Process at Konstant

  1. 1. WHITE PAPER: PROJECT ANALYSIS PROCESS PREPARED BY: KONSTANT INFOSOLUTIONS PVT. LTD. Disclaimer: The information contained in this white paper and other materials connected to this white paper and all discussions arising from it are confidential and are the property of Konstant Infosolutions Pvt. LTD. By accessing this document, you agree to keep confidential the information [Konstant Infosolutions Pvt Ltd.] | Confidential (including ideas, strategies etc.) contained within it or any discussions arising from it and re not to be disclosed.
  2. 2. INTRODUCTION This document will guide you about the procedures that Konstant follow in the Requirement Gathering Phase once the project is awarded to Konstant. As Konstant understands that requirement gathering is a vital part of successful project management and application development. We don’t want to blame the customers for not being sufficiently clear about their business requirements. Sometime clients/users are guided through a process that elicits their business requirements and facilitates accurate application development, but our analysts are well versed in both understanding the concepts of business requirement gathering AND the process that will best document them. THE ANALYSIS PROCESS Our analysts devote their time to the project RGP phase because we know that not defining the business data and system requirements at the start of a development project results in significant costs in subsequent Software Development Life cycle phases. The reason for this, we now know (after having a long experience of this industry), is that the analysis activity was simply shifted into other phases of the SDLC, resulting in additional effort and rework. Things are discovered during design, during coding, or during testing that should have been addressed during analysis. This causes lost time, increased effort (because of the ripple effect of the changes required) and increased project cost. Furthermore, costs are increased by changes to requirements during maintenance and enhancement activities, where companies currently spend an average of seventy-seven percent of a department's budget due to missing or incomplete requirements documentation. This complete document is describing the process that Konstant follows to analyze the client requirement in Requirement Gathering Phase. [Konstant Infosolutions Pvt Ltd.] | Confidential
  3. 3. Step I - Identification of Client’s Business Needs First of all our analysts identifies the needs of client’s business. For this , they find answers of following questions: What is the Definition of Business that Client has? What is the domain of client’s business? What are the goals of Business Organization? What are the core competencies? Once we get the answers of above questions, then we focus on understanding the needs of the business as a whole, its strategic direction, and identifying initiatives that will allow a business to meet those strategic goals. It also includes: Creating and maintaining the business architecture Conducting feasibility studies Identifying new business opportunities Scoping and defining new business opportunities Preparing the business case Conducting the initial risk assessment [Konstant Infosolutions Pvt Ltd.] | Confidential
  4. 4. Step II - Requirement Capturing from Clients It is essential for us that we perform a comprehensive business requirements gathering initiatives to see that application development can be a successful activity. For this, we follow the below techniques for collecting requirements from clients in a project: Document Analysis – In this phase we analyze the project details provided by the client. It can be any document, any reference website or applications, any idea provided from client initially. Our analysts spent considerable amount of time and interact with customers and review the input they provide. Focus Group – Once we complete with the initial analysis of the information provided from client side, we focus on the groups for which the proposed system will work. Those are also known as Identifications of Target Audience for the proposed project. Interviews – In this phase we conduct online meetings with our clients. We do these meetings via Skype, MSN, Yahoo Messenger, G-Talk or Phone Calls or any other communication channel that client prefers. In these meetings we interview subject matter from client and relate them with the project needs. We ask several possible questions from client and get their answers to understand the client’s vision and requirement in better way. This process is important to verify that client and we both are on the same grounds regarding the project understanding. [Konstant Infosolutions Pvt Ltd.] | Confidential
  5. 5. Step III - Requirement Analysis We use standard tools and practices to generate a single unambiguous baseline of the requirements after collecting the requirement from client side. The major forms of analysis that we use is as follows: Architecture Analysis – In this phase we identify the system architecture. The purpose of the Architecture Analysis is to facilitate system envisioning, by exploring and evaluating high level architectural options and to convey to the development teams and other stakeholders an early understanding of the high level structure of the intended system. The output of this phase is Architecture Diagram. For Example, the one on right hand side. Task Analysis – In this phase we identify the different tasks that system needs to perform in order to fulfill the business requirements. We create the list of these tasks and consider them while preparing the detailed specification document. The list of tasks is also known as features list of system. Interface Analysis – In this phase we identify the interface that project should have. What navigations, pages, their linking, content on each page, etc. identified in this phase of analysis. User Roles Analysis – What are the Roles and Responsibilities of each type of system users? We identify the answer of this question under this phase and list down all the possible roles and responsibilities of users. Brainstorming – Finally we perform the brainstorming sessions for the complex conditions that project may contain. For this we discuss the complex requirement in [Konstant Infosolutions Pvt Ltd.] | Confidential
  6. 6. group (business analysts and technical persons from the associated domains) and explore all the complex conditions of the project and their solutions according to the client’s business needs and technical feasibility. Step IV – Requirements Documentation Requirements documentation is the description of what a particular system does or shall do. It is used throughout development to communicate what the system does or shall do. It is a reference document or contract between the customer and the development team. The output of this step is System Requirement Specification Document (SRS). This document has following information about the system: Project Scope Definitions System Overview References Product Perspective Product Functions User Characteristics Constraints, Assumptions and Dependencies External interfaces Functions Performance requirements Logical database requirement Design constraints Key features [Konstant Infosolutions Pvt Ltd.] | Confidential
  7. 7. Following is the characteristics of the Specification Document that Konstant deliver to its clients: Correct Unambiguous Complete Consistent Ranked for importance and/or stability Verifiable Once the customer agrees to the SRS document the development team proceeds to develop the product conforming to all the requirements mentioned in the SRS document. [Konstant Infosolutions Pvt Ltd.] | Confidential
  8. 8. Step V – Flow Charts Designs A flow chart is a graphical or symbolic representation of the processes that a system have. The cool thing about flow charts is that it let you see the process flow of the complete system at a glance. It is a Snap Shot of the Business Processes. We prepare flow charts of the important process available in the system. It helps customers and developers to understand the process in better way. Following is the example of flow chart prepared by us for one of the projects: [Konstant Infosolutions Pvt Ltd.] | Confidential
  9. 9. Step VI – Wireframes Designs Wireframes, also known as a page schematic or screen blueprint, is a visual guide that represents the skeletal framework of a system. The wireframe depicts the page layout or arrangement of the website’s content, including interface elements and navigational systems, and how they work together. The wireframe usually lacks typographic style, color, or graphics, since the main focus lies in functionality, behavior, and priority of content placement. In other words, it focuses on “what a screen does, not what it looks like.” Following is an example: [Konstant Infosolutions Pvt Ltd.] | Confidential
  10. 10. Step VII – Client Approval This is the most IMPORTANT step in which we get the confirmation from client over all the deliverables we deliver to client in Requirement Gathering Phase like Specification Document, Flow Charts, Wireframes, etc. Once we get the client approval over all the deliverables, we forward the project to the next phase of design/development. Our designers and developers follow the instructions available in specification document and if client demands anything else that is not described in specification document then we treat that request as New Change Request. The analyst then again analyzes the New Change Request and provides the quote for new change to client. Above is the complete procedure that Konstant follows to understand the client requirement and to have a good start of project design and development that results in successful project completion. With this approach we have accomplished many successful websites and applications development in around all the domains and provided good revenue earning models to our clients. We hope that we will also have a long term business association with you as our client. Thanks for taking time to go through the document. Note: The document delivery can vary for different clients based upon project length, its complexity and budget. [Konstant Infosolutions Pvt Ltd.] | Confidential
  11. 11. About Konstant Infosolutions Pvt. Ltd. Konstant Infosolutions Pvt. Ltd expertise in providing variety of services and solutions in web development, application development and IT consulting services. Our vision is focused on customer satisfaction and is to render them topnotch quality. We vision toward competitive advantages for our clients through the innovative use of technology and to help them achieve long-term success and prosperity. For more information, contact mail@konstantinfo.com OR visit us at www.konstantinfo.com [Konstant Infosolutions Pvt Ltd.] | Confidential

×